System and Method for Extended Peripheral Component Interconnect Express Fabrics

ABSTRACT

An exemplary embodiment extended peripheral component interconnect express (PCIe) device includes a host PCIe fabric comprising a host root complex. The host PCIe fabric has a first set of bus numbers and a first memory mapped input/output (MMIO) space on a host CPU. An extended PCIe fabric includes a root complex endpoint (RCEP) as part of an endpoint of the host PCIe fabric. The extended PCIe fabric has a second set of bus numbers and a second MMIO space separate from the first set of bus numbers and the first MMIO space, respectively.

PRIORITY CLAIM AND CROSS-REFERENCE

This application is a continuation of U.S. patent application Ser. No.13/931,640, filed Jun. 28, 2013, entitled “System and Method forExtended Peripheral Component Interconnect Express Fabrics,” whichapplication is hereby incorporated herein by reference.

TECHNICAL FIELD

The present invention relates generally to the computing industry; and,more specifically to systems, methods, computer program products, andapparatuses for extending peripheral component interconnect express(PCIe) fabrics.

BACKGROUND

Peripheral component interconnect express (PCIe) is a high-speed serialcomputer expansion bus standard widely used to attach various hardwaredevices (e.g., storage devices, network cards, sound cards, and thelike) to a host central processing unit (CPU). Because the host CPUmemory configurations may be vendor-specific, PCIe provides for aninput/output (I/O) standard to connect various devices to the CPU. PCIeallows for a variety of improvements over older bus standards (e.g., PCIand PCI-eXtended). For example, PCIe generally allows for higher maximumsystem bus throughput, lower I/O pin count, smaller bus footprint,native hot-plug functionality, and other advantages.

An issue with the PCIe bus standard is that each PCIe fabric is limitedby a finite amount of resources. For example, each PCIe fabric's 32-bitaddress memory space may not exceed 4 GB in size, and each fabric mayonly have a maximum of 256 bus numbers. Because PCIe operates onpoint-to-point serial connections, these limitations directly cap themaximum number of nodes (i.e., devices) that may be attached to a PCIefabric. That is, bus numbers for various devices may not overlap, andeach attached device requires a set of unique bus numbers to function.Various bus numbers in a PCIe fabric may be reserved for particular uses(e.g., as internal bus numbers of PCIe switches, hot-plug functionality,or the like), further limiting the number of available bus numbers.

Furthermore, a fault occurring at any component attached to a PCIefabric may impact any other downstream or upstream components attachedto the faulty component. As the number of components and softwaredrivers attached to the PCIe fabric increases, fault handling becomesmore difficult and the propagation of any faults may lead to asystem-wide crash.

SUMMARY OF THE INVENTION

These and other problems are generally solved or circumvented, andtechnical advantages are generally achieved, by preferred embodiments ofthe present invention, which provide an extended peripheral componentinterconnect express fabric.

In accordance with one example embodiment, a peripheral componentinterconnect express topology includes a host PCIe fabric comprising ahost root complex. The host PCIe fabric includes a first set of busnumbers and a first memory mapped input/output (MMIO) space on a hostcentral processing unit (CPU). Further, an extended PCIe fabric isprovided, which includes a root complex endpoint (RCEP) as part of anendpoint of the host PCIe fabric. The extended PCIe fabric also includesa second set of bus numbers and a second MMIO space separate from thefirst set of bus numbers and the first MMIO space, respectively.

In accordance with another example embodiment, a peripheral componentinterconnect express (PCIe) topology includes an extended PCIe fabric.The extended PCIe fabric includes a root complex end point (RCEP). TheRCEP is configured to be part of an endpoint of a first level PCIefabric. In addition, the extended PCIe fabric comprises a memory mappedinput/output (MMIO) space and a set of bus numbers.

In accordance with yet another example embodiment, a method forconnecting peripheral includes providing a root complex endpoint (RCEP)hosting an extended peripheral component interconnect express (PCIe)fabric as part of an endpoint of a host PCIe fabric. The extended PCIefabric has a first MMIO space that is separate from a second MMIO spaceof the host PCIe fabric. The method further comprises mapping the firstMMIO space to the second MMIO space.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawing, in which:

FIG. 1 is a block diagram of a peripheral component interconnect express(PCIe) fabric in accordance with various example embodiments;

FIGS. 2A and 2B are block diagrams of PCIe configuration space mappingand addressing for an extended fabric in accordance with various exampleembodiments;

FIGS. 3A and 3B are block diagrams of 32-bit memory space mapping andaddressing for an extended fabric in accordance with various exampleembodiments;

FIGS. 4A and 4B are block diagrams of 64-bit memory space mapping andaddressing for an extended fabric in accordance with various exampleembodiments; and

FIG. 5 is a system diagram of a computing system having PCIe fabrics inaccordance with various example embodiments.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Example embodiments covering various aspects of the encompassedinnovation are discussed in greater detail below. It should beappreciated, however, that the present invention provides manyapplicable unique and novel concepts that can be embodied in a widevariety of specific contexts. Accordingly, the specific embodimentsdiscussed herein are merely illustrative of specific ways to make, use,and implement various aspects of the present invention, and do notnecessarily limit the scope thereof unless otherwise claimed.

The following various exemplary embodiments are described in a specificcontext, namely a peripheral component interconnect express (PCIe) busstandard fabric. As will be appreciated, however, such exampleembodiments may also extend other fabrics (e.g., upside down treetopologies with resource restrictions).

As described herein, a root complex is a hardware structure serving as abridge between a PCIe fabric and a host central processing unit (CPU).The root complex may be integrated as part of the CPU. For example, FIG.5 illustrates a root complex 502 as part of CPU 500. The root complexmanages and forwards various requests between the CPU and devices (e.g.,devices 506 and 508) connected to the same PCIe fabric (e.g., PCiefabric 504). The root complex also maps various connected devices(including device storage locations such as registers and memorylocations) onto PCIe memory space. These types of mapping and memoryspace are known as memory mapped input/output (MMIO) space.

Also as used herein, MMIO space may include a portion of memoryaddressable using 32-bit addresses, which is generally limited to thefirst 4 GB of MMIO space. The MMIO space may further include a portionof memory addressable using 64-bit addresses, which may be mapped toMMIO space above the first 4 GB. Various example embodiments describedherein include one or more additional root complex hardware structuresas part of the endpoints of the host PCIe fabric. By adding root complexfunctionalities to endpoints (referred to as a root complex endpoint(RCEP)), additional PCIe fabrics may be connected to form extended PCIefabrics that are not limited to the finite resources of the host PCIe.

For example, FIG. 5 illustrates a RCEP 508 and an extended PCIe fabric510 connecting additional endpoints (e.g., device 512 and 514) to hostCPU 500. In accordance with various exemplary embodiments, these RCEPsmay be used to isolate faults from contaminating bordering fabrics ordevices. Furthermore, other example embodiments provide that the RCEPsand extended PCIe fabrics can be compatible with existing peripheraldevice drivers; thus, eliminating any need for software updates toexisting device drivers.

FIG. 1 illustrates a block diagram of a first level PCIe fabric 100connected to an extended PCIe fabric 118 in accordance with variousexemplary embodiments. The PCIe fabric 100 may include a host rootcomplex 102 that manages and forwards various requests between the hostCPU and various devices connected to PCIe fabric 100. Generally, rootcomplex 102 owns a set of 256 unique bus numbers and MMIO space, and itmaps various connected devices (including their associated registersand/or memory hardware) to its MMIO space. Further, root complex 102 mayinclude a root port 103, which is a hardware bridge structure allowingfor PCI-to-PCI connections between the host CPU and the devicesconnected to PCIe fabric 100 (e.g., endpoints 106 and 108). AlthoughFIG. 1 illustrates root complex 102 as having only one root port 103, atypical root complex 102 may have multiple root ports 103 (e.g., betweenfour to six root ports).

As shown in FIG. 1, root complex 102 is electrically connected toendpoints 106 and 108 through root port 103 and a switch 104. Typically,endpoints 106 and 108 are structures that terminate PCIe fabric 100.Such endpoints 106 and 108 may include storage devices, networkingdevices, sound cards, video cards, and the like. Also illustrated inFIG. 1 is switch 104, which may include at least one upstream port (port104A) and numerous downstream ports (e.g., ports 104B) interconnectingvarious endpoints (e.g., 106 and 108) to root complex 102. As generallyused herein, an upstream port refers to a port that points towards thehost root complex (e.g., root complex 102), while a downstream portrefers to a port that points away from it.

Switch 104 may include internal buses that allow multiple devices to beconnected to a single root port 103 while still maintaining apoint-to-point serial connection used by the PCIe standard. AlthoughFIG. 1 only illustrates one switch 104 connecting two endpoints 106 and108 to root port 103, various exemplary embodiments contemplate multipleroot ports connected to any number of switches, wherein each switch maybe connected to any varying number of endpoints. Alternatively, or inconjunction, a root port 103 may be connected directly to an endpoint.Accordingly, the configuration illustrated in FIG. 1 and other figuresherein is for illustrative purposes only and is not meant to limit orotherwise narrow the scope of the present invention unless otherwiseexplicitly claimed.

As shown in FIG. 1, endpoint 106 may be a root complex endpoint (RCEP)in accordance with exemplary embodiments, which provides a hardwarebridge between extended PCIe fabric 118 and first level PCIe fabric 100.That is, RCEP 106 may host extended PCIe fabric 118. In accordance withsuch embodiments, RCEP 106 may be similar in build and logic to a hostroot complex (e.g., root complex 102). As such, RCEP 106 may include itsown set of bus numbers, PCIe configuration space, and MMIOspace—separate from those of root complex 102. Therefore, additionaldevices may be connected to RCEP 106 even when root complex 102 does nothave a sufficient amount of available resources (e.g., bus numbers).

For example, endpoints 114 and 116 may be electrically connected to RCEP106 through switch 112 and root port 110. As noted above, endpoints 114and 116 may be most any type of peripheral devices, including storagedevices, networking devices, sound cards, video cards, and the like.Similar to previous PCIe fabrics, endpoints 114 and 116 may simplyterminate extended PCIe fabric 118. Alternatively, and in accordancewith exemplary embodiments, endpoints 114 and/or 116 may include anotherRCEP having its own set of bus numbers and MMIO space; thus, forminganother extended PCIe fabric. Accordingly, RCEPs essentially add gatewayfunctionality to a PCIe endpoint; and therefore, theoretically, allowfor a virtually limitless number of nodes to be attached to a host rootcomplex.

Although FIG. 1 shows extended PCIe fabric 118 as having only one rootpoint 110, one switch 112, and two endpoints 114 and 116, variousembodiments may include an extended PCIe fabric having multiple rootports, multiple switches per extended fabric, and multiple endpoints perswitch.

In accordance with exemplary embodiments, RCEP 106's MMIO may include aportion addressable using 32-bit addresses (referred to as 32-bit memoryspace) and a portion using 64-bit addresses (referred to as 64-bitmemory space). In accordance with such embodiments, RCEP 106's PCIeconfiguration space, 32-bit memory space, and 64-bit memory space may bemapped to the 64-bit MMIO space of host PCIe fabric 100 (i.e., theportion of PCIe fabric 100's MMIO space that is addressable using 64-bitaddresses). Thus, in accordance with such embodiments, RCEP 106 may beaccessed from the MMIO space of host PCIe fabric 100. The mapping andenumeration of RCEP 106's extended fabric may be done using endpointdrivers associated with RCEP 106, as explained in greater detail below.

In accordance with other exemplary embodiments, RCEP 106 may alsoinclude fault handling mechanisms that resolve any faults occurring inits downstream devices (e.g., endpoints 114 and 116). Therefore, in suchembodiments, faults may be contained by RCEP 106 and not propagateupstream to PCIe fabric 100, and RCEP 106 may act as a fault boundary.Further, RCEP 106 may generate an error interrupt to notify host rootcomplex 102 of any faults. In such embodiments, these error interruptsmay be used as a reporting mechanism, and any PCIe faults occurring inRCEP 106's downstream devices may be handled by RCEP 106 and not passedupstream to host root complex 102. The specific details regarding errorinterrupt reporting and fault handling may be implementation specificand vary between computing platforms/root complexes. For example,current PCIe standards leave the implementation details regarding how aroot complex handles faults open to different varying vendor-specificimplementations of computing platforms/root complexes. Therefore, theimplementation details of RCEP 106's fault handling and error reportingmechanisms may, similarly, be open to different implementationsdepending on the applicable computing platform/root complexconfigurations.

Mapping and accessing PCIe configuration space for extended fabric 118may be done using any suitable configuration. For example, FIGS. 2A and2B illustrate an example of PCIe configuration space mapping and accessin accordance with exemplary embodiments, which support using MMIO toaccess PCI configuration space. Generally, physical address space 200 isthe physical address space of the host CPU, which may be, e.g., 2^(n)-1bytes in size (where “n” is the number of physical address bitsimplemented by the host CPU). As shown, physical address space 200 mayinclude a portion of space 202 addressable via 32-bit physical addresseswith a remaining portion 204 addressable via 64-bit physical addresses.In such embodiments, portion 202 may occupy the first 4 GB of addressspace 200, while portion 204 may occupy the remainder of address space200. Moreover, portion 204 may further include a portion allocated to64-bit MMIO space 206 of the host, first-level PCIe fabric (e.g., PCIefabric 100). Of course, other memory allocations, configurations andmappings of the MIMO space to PCIe fabric are contemplated herein; andthus, any specific implementation described herein is used forillustrative purposes only—unless otherwise explicitly claimed.

In accordance with exemplary embodiments, all (or any portion) of adevice's functions connected to PCIe fabric 100 or extended fabric 118may be mapped to their respective fabrics' own dedicated 256 MB ofconfiguration space. Such space may be addressable, for example, byknowing the 8-bit PCI bus, 5-bit device, and 3-bit function numbers fora particular device function. This type of function addressing may bereferred to herein as bus/device/function (BDF) addressing, which allowsfor a total of 256 bus numbers, 32 devices, and 8 functions for eachPCIe fabric. Generally, in such embodiments, the device number may beset to 0 in accordance with PCIe bus standard fabrics due to PCIe'sserial point-to-point connection structure. Further, in accordance withsuch embodiments, each device function may be entitled to 4 KB ofconfigurations registers.

As shown, PCIe configuration space for the first level PCIe fabric(e.g., fabric 100) may occupy 256 MB of address space 208 in portion ofspace 202. In such embodiments, PCIe configuration space for theextended PCIe (e.g., extended fabric 118) may be mapped to 256 MB ofaddress space 210 in 64-bit MMIO space 206. Further, any MMIOtransactions in address spaces 208 or 210 may be treated as PCIeconfiguration access transactions for either PCIe host fabric 100 orextended fabric 118, respectively, by their corresponding root complex.

In such embodiments, the addresses of extended PCIe configuration space210 may start at base value 212. Thus, the configuration space registersof a PCIe device function located at bus number B, device number D, andfunction number F may start at, for example, Base+(B+D+F)*4K.Alternatively, other suitable configurations for addressing device spaceregisters are also contemplated, and the description of BDF addressinghere is used for illustrative purposes only.

FIG. 2B illustrates an example PCIe device physical address format 220in accordance with example embodiments. Format 220 may include a basefield 222 (located, e.g., between bits n−1 and 28), a bus field 224(located, e.g., between bits 27 and 20), a device field 226 (located,e.g., between bits 19 and 15), and a function field 228 (located e.g.,between bits 14 and 12). Moreover, in such embodiments, bits 11 to 0 maycontain an offset of the configuration space register (e.g., within thedevice) being accessed, which may be included, e.g., for memoryalignment purposes.

Mapping and accessing 32-bit memory space for extended PCIe fabric 118may be done using any suitable configuration. For example, FIGS. 3A and3B illustrate an example of PCIe 32-bit memory space mapping and accessin accordance with exemplary embodiments. Generally, 32-bit memory spaceaccess may be used for device register banks that may be accessed with32-bit addresses. In such embodiments, corresponding transactions may bemarked as 32-bit PCIe memory space access, e.g., in a PCIe packetheader. Of course, other memory allocations, configurations and mappingsof the MIMO space to PCIe fabric are contemplated herein; and thus, anyspecific implementation described herein is used for illustrativepurposes only—unless otherwise explicitly claimed.

Under current PCIe standards, the maximize size for a 32-bit addressspace is 4 GB. Furthermore, in accordance with current PCIe standards,on certain computing platforms (e.g., x86 platforms) the 32-bit memoryfor first-level PCIe fabric 100 may be shared with its PCIeconfiguration space and, thus, may be only 256 MB in size.

In accordance with exemplary embodiments, extended PCIe fabric 118 mayhave its own 32-bit memory space separate from the physical addressspace 200 of the host CPU. Moreover, as shown in FIG. 3A, RCEP 106 maymap extended fabric 118's 32-bit address space to a higher 64-bitaddress window on the host's 64-bit MMIO space 206 as illustrated bymemory space 302. In such embodiments, memory space 302 may be separatefrom the 32-bit memory space 300 for the first level fabric (e.g., PCIefabric 100). Further, memory space 300 may be located at the host CPU's32-bit addressable space 202, which may be within the same low 4G spaceas PCIe configuration space 208. As shown, memory space 302 starts at abase address 304 and may be up to 4 GB in size. Thus, in accordance withsuch embodiments, a device register bank (e.g., register bank 308) maybe addressed by knowing the appropriate offset (e.g., offset 306) of theregister bank. That is, the address of register bank 308 may base304+offset 306. Alternatively, other suitable schemes for addressingregister bank 308 are also contemplated.

FIG. 3B illustrates register bank physical address formats 310 and 312for host address space and extended fabric address space, respectivelyin accordance with example embodiments. Format 310 may include a basefield 314 (e.g., occupying bits n−1 to 32) and an offset field 316(e.g., occupying bits 31 to 0). In such embodiments, format 310 may beused to address a device register bank mapped to MMIO space 206. Format312 may only contain an offset field 318 (e.g., occupying 32 bits) foraddressing the device register bank on the extended fabric (e.g., fabric118). Moreover, before placing a PCie packet on extended fabric 118,RCEP 106 may strip the upper 32-bits format 310 (which may be 64-bitslong) and mark the stripped PCIe packet as a 32-bit address packet.

Mapping and accessing 64-bit memory space for extended PCIe fabric 118may be done using any suitable configuration. For example, FIGS. 4A and4B illustrate an example of 64-bit memory space mapping and access inaccordance with exemplary embodiments. Generally, 64-bit memory spaceaccess may be used for device register banks that can be accessed with64-bit addresses or 32-bit addresses. Note, that if a 32-bit addressrange is assigned to a 64-bit address, the PCIe hardware may use a32-bit PCI memory space configuration scheme to access (e.g., theconfiguration described in FIGS. 3A and 3B). In such embodiments,corresponding transactions may be marked as 64-bit PCIe memory spaceaccess in a PCIe packet header. Moreover, for historical reasons, the64-bit memory space may generally be located above the lower 4 GB ofphysical address space. Of course, other memory allocations,configurations and mappings of the MIMO space to PCIe fabric arecontemplated herein; and thus, any specific implementation describedherein is used for illustrative purposes only—unless otherwiseexplicitly claimed.

In such embodiments, extended PCie fabric 118 may have its own 64-bitmemory space separate from the physical address space 200 of the hostCPU. As shown in FIG. 4A, RCEP 106 may map extended fabric 118's 64-bitaddress space to the host CPU's 64-bit MMIO space 206 as illustrated bymemory space 402. Further, memory space 402 may be separate from a64-bit PCIe memory space 400 of the first level fabric 100, which mayalso be located in 64-bit MMIO space 206. In such embodiments, Memoryspace 402 may start at a base address 404 and may be, for example, mtimes 4 GB in size (where m is a constant, signifying that space 402 mayhave a size of one or more times 4 GB). Furthermore, a device registerbank (e.g., register bank 408) may be addressed by knowing anappropriate offset (e.g., offset 406) of the register bank. Thus, inaccordance with such embodiments, an address of register bank 408 may bebase 404 plus offset 406. Alternatively, other suitable schemes foraddressing register bank 408 are also contemplated.

FIG. 4B illustrates register bank physical address formats 410 and416/418 for host CPU address space and extended fabric address space,respectively in accordance with example embodiments. Format 410 mayinclude a base field 412 (e.g., occupying bits n−1 to p) and an offsetfield 414 (e.g., occupying bits p−1 to 0). The value of constant p maybe 32+ln(m), which may be rounded to the next highest integer value.Format 410 may be used to address a device register bank mapped to64-bit MMIO space 206.

In certain exemplary embodiments, addressing the device register bank onthe extended fabric 118 may be done using format 416. For example,format 416 may be used if the base physical address is size aligned toextended fabric 118's memory space configuration. Using format 416, RCEP106 may strip the upper bits (e.g., bits 63 to p) of format 410 to forma 64-bit address for extended fabric 118. In other exemplaryembodiments, format 418 may be used if the base physical address is notsize aligned to extended fabric 118's memory space. In such embodiments,in order to compensate for the non-alignment of the physical address, anoffset 420 may be added to a 64-bit system base address 422. Moreover,if the base address is at least 4 GB aligned (e.g., the lower 32-bitsare 0) the size adjustment may only be performed for the high 32-bits ofthe base address.

In an exemplary embodiment, extended fabric 118's PCIe configurationspace 210, 32-bit memory space 302, and 64-bit memory space 402 mayoverlap in the host CPU. In such embodiments, RCEP 106 may request acommon mapping window large enough to accommodate all desired addressranges (e.g., spaces 210, 302, and 402) from the host CPU, and RCEP 106may then divide the common mapping window as necessary into variousdesired address ranges.

In accordance with exemplary embodiments, extended fabric 118 maysupport device interrupts, which may be handled using any suitablemethod. For example, extended fabric 118 may use a message signaledinterrupt (MSI) configuration. In such embodiments, MSIs originatingfrom devices connected to extended fabric 118 (e.g., endpoints 114 and116) may be delivered to applicable root ports (e.g., root port 110) inaccordance with the PCIe bus standard. Furthermore, root port 110 ofRCEP 106 may have a pre-assigned address window for MSIs. In suchembodiments, when a memory write address matches the pre-assigned MSIaddress window, the transaction may be recognized as an interrupt.Moreover, Root port 110 may collect all the MSIs originating from itsdownstream fabrics and deposit them into a queue (where the queue may belocated in the host CPU's memory in physical address space 200). Rootport 110 may then signal a separate interrupt, which may also be a MSI,to its upstream root port (e.g., host root port 103). Host root port 102may then trigger an appropriate software handler in accordance with thereceived interrupt. An interrupt handler of RCEP 106's root port 110 maythen examine the MSI queue in main memory, determine the originatingdevice (e.g., endpoint 114 or 116), and dispatch the appropriateinterrupt handler of the device driver. Of course, other schemes forhanding device interrupts are contemplated herein; and thus, anyspecific implementation described herein is used for illustrativepurposes only—unless otherwise explicitly claimed.

In accordance with other exemplary embodiments, extended fabric 118 mayalso support direct memory access (DMA), which may be handled using anysuitable method. In such embodiments, DMA transactions may include readrequests, read completions, and write requests. PCIe packets may carry asystem physical address or an IO (input/output) virtual addresstranslated by an IOMMU (input/output memory management unit). Moreover,the PCIe requester IDs may be per fabric. Thus, the requester IDs may bereplaced with RCEP 106's ID when a request crosses a PCIe fabricboundary and goes upstream to host PCIe fabric 100. That is, on extendedfabric 118, the requester ID may be the ID of the endpoint device (e.g.,endpoint 114 or 116). As the request gets forwarded upstream to rootcomplex 102, the requester ID may be replaced with the ID of RCEP 106.

In such embodiments, DMA writes refer to moving data from a device(e.g., endpoint 114 or 116) to the host CPU's memory. RCEP 106 mayreplace the device ID with RCEP 106's ID when the request is passedupstream by RCEP 106 to root complex 102 and the host CPU. Furthermore,DMA reads refer to moving data from the host CPU's memory to the device.In such embodiments, RCEP 106 may utilize a hardware scoreboard to trackall read requests by assigning transaction tags (e.g., as part of therequest packets) for transactions to fabric 100. These transaction tagsmay be linked to RCEP 106's score board entries and may be used torecord the requester IDs of read request packets originating on extendedfabric 118. Completion data received by RCEP 106 from root complex 102may carry the same transaction tag as the corresponding read request inaccordance with such embodiments. Thus, in such embodiments, transactiontags may be used to match against score board entries to determine theappropriate device ID used on extended fabric 118. Of course, otherschemes for handing DMA requests are contemplated herein; and thus, anyspecific implementation described herein is used for illustrativepurposes only—unless otherwise explicitly claimed.

Therefore, using the various PCIe configuration access, memory access,DMAs, and interrupt mechanisms described in exemplary embodiments of theabove paragraphs, RCEP devices may be used to host extended PCIe fabricsand connect additional devices (e.g., additional RCEP devices and/orperipheral devices) to a host root complex. RCEP devices may be similarto a typical PCIe root complex logic. Each extended PCIe fabric may haveits own MMIO space and set of bus numbers. Therefore, the total numberof devices that may be connected to a host CPU may not limited to thenumber of available bus numbers of the host PCIe fabric. In suchembodiments, the MMIO space of each of the extended fabric may mapped tothe 64-bit MMIO space of its parent fabric (e.g., the parent fabric forextended fabric 118 is first level fabric 100) for ease of access.Furthermore, fabric enumeration of the extended fabrics may be achievedthrough the RCEP endpoint device driver. In such embodiments, each RCEPmay handle faults originating on the applicable extended root complexfabric. Thus, fault isolation may be achieved so that downstream fabricfaults may be intercepted at the fabric boundary of an extended PCIefabric and not propagated upstream.

In accordance with exemplary embodiments, almost any peripheral device(e.g., sound cards, video cards, network drivers, memory cards, and thelike) may be connected to the extended fabric and need not change theirdriver software. In such embodiments, the extended PCIe fabric isinteracts with peripheral devices in the same manner as a first levelPCIe fabric. Moreover, the host CPU's software (e.g., an operatingsystem) and RCEP drivers may be modified and/or created to set upregister mapping, DMA address mapping, implement interrupt handlersthrough the RCEP, and other similar functions. Therefore, peripheraldevices need not be notified that they are connected to an extended PCIefabric instead of a first level PCIe fabric. Thus, extended PCIe fabricsand RCEP may be compatible with existing peripheral device drivers.

While this invention has been described with reference to illustrativeexemplary embodiments, this description is not intended to be construedin a limiting sense. Various modifications and combinations of theillustrative exemplary embodiments, as well as other embodiments of theinvention, will be apparent to persons skilled in the art upon referenceto the description. It is therefore intended that the appended claimsencompass any such modifications or embodiments.

I claim:
 1. A peripheral component interconnect express (PCIe) topologycomprising: a host PCIe fabric connected to a host central processingunit (CPU), wherein the host PCIe fabric comprises a host root complexand has a first set of bus numbers; and an extended PCIe fabriccomprising a root complex endpoint (RCEP) as part of an endpoint of thehost PCIe fabric, wherein the extended PCIe fabric having a second setof bus numbers separate from the first set of bus numbers, wherein thehost PCIe fabric is a bridge between the extended PCIe fabric and thehost CPU, and wherein the second set of bus numbers allows additionaldevices to be connected to the host CPU beyond a capacity of the hostPCIe fabric as provided by resources of the host root complex.
 2. ThePCIe topology of claim 1, wherein the host PCIe fabric has a firstmemory mapped input/output (MMIO) space on the host CPU, and wherein theextend PCIe fabric has a second MMIO space separate from the first MMIOspace.
 3. The PCIe topology of claim 2, wherein the second MMIO space ofthe extended PCIe fabric is mapped to a physical address space on thehost CPU.
 4. The PCIe topology of claim 3, wherein the physical addressspace is the first MMIO space.
 5. The PCIe topology of claim 4, whereina memory space of the extended PCIe fabric is mapped to a 64-bit MMIOspace of the first MMIO space.
 6. The PCIe topology of claim 2, whereina PCIe configuration space of the extended PCIe fabric is mapped to thefirst MMIO space.
 7. The PCIe topology of claim 6, wherein each devicefunction of the extended PCIe fabric is mapped to a respective fourkilobytes of a 64-bit MMIO space of the first MMIO space.
 8. The PCIetopology of claim 6, wherein the PCIe configuration space of theextended PCIe fabric is mapped to a different part of the first MMIOspace as a PCIe configuration space of the host PCIe fabric.
 9. The PCIetopology of claim 1, wherein the RCEP is configured to isolate faultsoriginating on the extended PCIe fabric from propagating to the hostPCIe fabric.
 10. The PCIe topology of claim 1, wherein the extended PCIefabric interacts with a peripheral device in a same manner as the hostPCIe fabric.
 11. An extended PCIe fabric comprising: a root complex endpoint (RCEP) device configured to be part of an endpoint of afirst-level PCIe fabric, wherein the first-level PCIe fabric isconfigured to be a bridge between the extended PCIe fabric and a hostcomputer processing unit (CPU); a first memory mapped input/output(MMIO) space separate from a second MMIO space of the first-level PCIefabric; and a set of bus numbers allowing additional devices to beconnected to the host CPU beyond a capacity of the first-level PCIefabric as provided by resources of a first-level root complex of thefirst-level PCIe fabric.
 12. The extended PCIe fabric of claim 11,wherein the first MMIO space is mapped to the second MMIO space of thefirst-level PCIe fabric on the host CPU.
 13. The extended PCIe fabric ofclaim 11, a PCIe configuration space of the extended PCIe fabric ismapped to the second MMIO space of the first-level PCIe fabric on thehost CPU.
 14. The extended PCIe fabric of claim 11, wherein an endpointof the extended PCIe fabric is an additional RCEP device of anadditional extended PCIe fabric, wherein the additional extended PCIefabric comprises an additional set of bus numbers allowing additionaldevices to be connected to the host CPU beyond a capacity of thefirst-level PCIe fabric as provided by resources of the first-level rootcomplex of the first-level PCIe fabric and a capacity of the extendedPCIe fabric as provided by resources of the RCEP of the extended PCIefabric.
 15. A method comprising: including a root complex endpoint(RCEP) hosting an extended peripheral component interconnect express(PCIe) fabric as part of an endpoint of a host PCIe fabric, wherein theextended PCIe fabric comprises: a first MMIO space that is separate froma second MMIO space of the host PCIe fabric; and a first set of busnumbers that is separate from a second set of bus numbers of the hostPCIe fabric, wherein the first set of bus numbers allows additionaldevices to be connected to a host computer processing unit (CPU) beyonda capacity provided by resources a host root complex of the host PCIefabric.
 16. The method of claim 15 further comprising mapping the firstMMIO space of the extended PCIe fabric to the second MMIO space of thehost PCIe fabric, wherein the second MMIO of the host PCIe fabric isstored on a physical address on the host CPU, and wherein the host PCIefabric is a bridge between the extended PCIe fabric and the host CPU.17. The method of claim 15 further comprising intercepting, by the RCEP,downstream faults occurring on the extended PCIe fabric.
 18. The methodof claim 15 further comprising: including an additional RCEP hosting anadditional extended PCIe fabric as part of an endpoint of the extendedPCIe fabric, wherein the additional extended PCIe fabric comprises: athird MMIO space separate from the first MMIO space and the second MMIOspace; and a third set of bus numbers separate from the first set of busnumbers and the second set of bus numbers, wherein the third set of busnumbers allows additional devices to be connected to the host CPU beyonda capacity provided by resources the host root complex and a capacityprovided by resources of the RCEP.
 19. The method of claim 15 furthercomprising handling, by the RCEP, device interrupts originating on theextended PCIe fabric using message signaled interrupts (MSIs).
 20. Themethod of claim 15 further comprising handling a direct memory access(DMA) request from a device connected to the extended PCIe fabric byreplacing an originating device ID in a DMA request with a RCEP ID whenthe DMA request is forwarded upstream to the host PCIe fabric.